Skip to content

Fix kernel update issue if version is different, release is the same - #10

Merged
jdieter merged 1 commit into
mainfrom
fix-version-detection
Feb 3, 2026
Merged

Fix kernel update issue if version is different, release is the same#10
jdieter merged 1 commit into
mainfrom
fix-version-detection

Conversation

@jdieter

@jdieter jdieter commented Feb 3, 2026

Copy link
Copy Markdown
Collaborator

This doesn't come up in EL kernels, but is a problem for custom kernels.

This doesn't come up in EL kernels, but is a problem for custom kernels.

Signed-off-by: Jonathan Dieter <jdieter@ciq.com>

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR fixes an issue where kernel updates were incorrectly blocked when custom kernels had different versions but the same release number (e.g., 5.10.0-1 vs 5.10.1-1). The fix ensures that packages built from the same kernel source RPM are properly identified by filtering on both version and release, rather than just release alone.

Changes:

  • Updated two filter() calls in src/protected_kmods.py to filter by both version and release instead of just release
  • Bumped version to 1.0.1 and added changelog entry in the spec file

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
src/protected_kmods.py Added version parameter to two filter() calls that assemble lists of packages from the same kernel source RPM, ensuring accurate filtering when version differs but release is the same
dnf-plugin-protected-kmods.spec Version bump to 1.0.1 and added changelog entry documenting the fix

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@jdieter
jdieter merged commit fc3a805 into main Feb 3, 2026
7 checks passed
@jdieter
jdieter deleted the fix-version-detection branch February 3, 2026 18:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants